Ev operator specific parameter(s) communicated between pev and evse

ABSTRACT

An electric vehicle supply equipment (EVSE) receives, from an electric vehicle (EV) connected to the EVSE, one or more electric vehicle (EV) operator-specific parameters that are specific to an EV operator, where the one or more EV operator-specific parameters affect charging service for the EV at the EVSE, and where the one or more EV operator-specific parameters are received automatically as a result of the EV being connected to the EVSE. The EVSE applies the one or more EV operator-specific parameters.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/136,849, filed Apr. 22, 2016, which claims the benefit of U.S.Provisional Application No. 62/152,751, filed Apr. 24, 2015, which areall hereby incorporated by reference.

FIELD

Embodiments of the invention relate to the field of charging electricvehicles; and more specifically, to communicating electric vehicle (EV)operator specific parameter(s) between a plug-in electric vehicle (PEV)and electric vehicle supply equipment (EVSE).

BACKGROUND

Electric vehicle supply equipment (EVSE), sometimes referred to as anelectric vehicle charging station, is used to charge plug-in electricvehicles (PEVs, such as electric battery powered vehicles,gasoline/electric battery powered vehicle hybrids) (PEV is sometimesreferred herein as an electric vehicle (EV)). EVSEs may be located indesignated charging locations (e.g., similar to locations of gasstations), adjacent to parking spaces, at residences, etc.

An EV operator may be associated with an account with a Charging ServiceProvider (CSP) that may have preferences and/or settings that arespecific to the EV operator. Example preferences and/or settings includecost/pricing parameter(s) (e.g., the cost of power that the EV operatoris willing to pay for electrical energy at various times throughout theweek and/or for one or more types of charging service (workplace, publicparking, home)), access credentials and/or roaming parameters for “home”and “foreign” CSPs; alerts and notification preferences (e.g., the typeand frequency of alerts and notifications concerning a charging sessionthat the driver wishes to receive), etc. These preferences and/orsettings may be entered, viewed, and/or managed by the EV operatorthrough a service portal (using a web browser and/or smartphone/tabletapp) provided by the EV manufacturer and/or CSP.

PEV specific preferences can be set and/or managed through the PEV'sin-cabin (dashboard) user interface. These PEV specific parameters arenot EV operator-specific. Therefore, different EV operators with accessto the same PEV (e.g., family members or users of a fleet of sharedEVs), cannot practically use this method to set or choose different EVoperator specific preferences.

Currently, data exchange between the PEV and the EVSE is limited to theparameters related to the embedded control of energy transfer andrelated safety provisions. Neither PEV-level nor PEV operator-specificparameters can be exchanged between the PEV and EVSE.

SUMMARY

An electric vehicle connected to electric vehicle supply equipment(EVSE) transmits, to the EVSE, EV operator-specific parameters that arespecific to an EV operator to the EVSE, where the EV operator-specificparameter(s) affect charging service for the EV at the EVSE, and wherethe one or more EV operator-specific parameters are receivedautomatically as a result of the EV being connected to the EVSE. TheEVSE applies or affects the EV operator-specific parametersappropriately.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention may best be understood by referring to the followingdescription and accompanying drawings that are used to illustrateembodiments of the invention. In the drawings:

FIG. 1 illustrates an exemplary system where EV operator-specificparameters are communicated between an electric vehicle and an EVSEaccording to one embodiment;

FIG. 2 is a flow diagram that illustrates exemplary operations accordingto some embodiments of the invention;

FIG. 3 illustrates an exemplary EVSE according to one embodiment; and

FIG. 4 is a block diagram illustrating an exemplary architecture of adata processing system that may be used in some embodiments.

DESCRIPTION OF EMBODIMENTS

In the following description, numerous specific details are set forth.However, it is understood that embodiments of the invention may bepracticed without these specific details. In other instances, well-knowncircuits, structures and techniques have not been shown in detail inorder not to obscure the understanding of this description. Those ofordinary skill in the art, with the included descriptions, will be ableto implement appropriate functionality without undue experimentation.

References in the specification to “one embodiment,” “an embodiment,”“an example embodiment,” etc., indicate that the embodiment describedmay include a particular feature, structure, or characteristic, butevery embodiment may not necessarily include the particular feature,structure, or characteristic. Moreover, such phrases are not necessarilyreferring to the same embodiment. Further, when a particular feature,structure, or characteristic is described in connection with anembodiment, it is submitted that it is within the knowledge of oneskilled in the art to effect such feature, structure, or characteristicin connection with other embodiments whether or not explicitlydescribed.

A method and apparatus for communicating EV operator-specific parametersbetween a PEV to an EVSE is described herein. In one embodiment of theinvention, a set of EV operator-specific parameters that can affect thecharging services of that EV operator is communicated between the EV andEVSE. This communication may be over a TCP/IP protocol stack (supportingInternet-style packet-based messaging) such as provided by industrystandards ISO/IEC 15118 and SAE J2847/J2931. Examples of the EVoperator-specific parameters include the cost of power that a driver iswilling to pay for electrical energy at various times throughout theweek, for each type of charging service (workplace, public parking,home); the driver's access credentials and roaming parameters, for‘home’ and ‘foreign’ Charging Service Providers (CSPs); the type andfrequency of alerts and notifications concerning a charging session thatthe driver wishes to receive; etc.

In one embodiment of the invention, the set of EV operator-specificparameters is communicated to the EVSE automatically upon the EV beingconnected to the EVSE. The set of EV operator-specific parameters may becommunicated across a wired connection and/or a wireless connection. Forexample, in the case of a wired connection between the EV and the EVSEwhere typically a charging cable connects the EV and EVSE, the EVoperator-specific parameters may be communicated to the EVSE across thecharging cable. As another example, a wireless connection may beestablished between the EV and the EVSE that can be used to communicatethe EV operator-specific parameters (which may be required in case ofinductive charging).

FIG. 1 illustrates an exemplary system where EV operator-specificparameters are communicated between the EV 110 and the EVSE 120according to one embodiment. The network server 125, among other things,stores EV operator profiles 150 of EV operators, where each EV operatorprofile includes one or more preferences and other settings, choices,and/or other parameters that can affect that EV operator's chargingservices and shape their charging experience. One example of theinformation that may be included in an EV operator profile is anindication of which offered charging plans (e.g., cost of energy, amountof energy, “renewable only” energy, etc.), in priority order, are to beused at different classes of sites (e.g., business, home, commercial) atdifferent times of days (e.g., work hours, weekday, weekend, etc.),etc., and/or the amount that the EV operator is willing to pay forcharging service for those different plans. As an example, at work, theathletic club, any public parking facility, for DC Fast charging, the EVoperator is willing to pay up to X dollars for parking at a DC Fastcharging spot and up to $Y/mile or /kWh, or up to $Z for charging to Wmiles range or V % battery charge. Another example of the informationthat may be included in an EV operator profile is an indication of EVoperator-specific credits or discounts (e.g., loyalty discounts) thatmay be applicable (e.g., 10% discount for using certain EVSEs at certainmember locations). Another example of the information that may beincluded in an EV operator profile is the EV operator's accesscredentials and/or roaming parameters for “home” and “foreign” ChargingService Providers (CSPs). Another example is the type and frequency ofalerts and notifications concerning a charging session that the driverwishes to receive (e.g., battery full; session will be over in Xminutes; request to move vehicle, etc.) and notification message contactinformation (e.g., email address(es), phone number(s), username(s),etc.)

The network server 125 may be owned and/or operated by a CSP.Alternatively, the network server 125 may be owned and/or operated by anEV manufacturer. The information in an EV operator profile may beestablished through use of a web portal, mobile phone application,dashboard interface in the EV, and/or other interface, by the EVoperator and/or on behalf of an EV operator (e.g., a fleet manager maycreate EV operator profiles for members of the fleet, an employer maycreate EV operator profiles for its employees, etc.). Certaininformation in an EV operator profile may be established or created bythe CSP and/or EV manufacturer.

The EV operator profiles are communicated to the appropriate electricvehicles specified in the profile. For example, the electric vehicle 110is associated with the EV operator profiles 130A-N, where N is greaterthan or equal to 1, and the EV operator profiles 130A-N are communicatedto the EV 110 accordingly. By way of example, the EV 110 may beassociated with a profile specific to a first EV operator (e.g., a firstfamily member) and another profile specific to a second EV operator(e.g., a second family member). As another example, the EV 110 may beassociated with a profile specific to an EV operator's work and anotherprofile specific to the EV operator's personal use. The EV operatorprofiles 130A-N may be communicated to the EV 110 differently indifferent embodiments, such as through use of a vehicle telematics link,through use of a paired mobile device, or through other mechanisms.

The EV 110 receives and stores the EV operator profiles 130A-N (e.g., inon-board non-volatile memory such as NAND or NOR flash memory). In oneembodiment, the EV 110 is configured to transmit at least some of theinformation included in the EV operator profiles 130A-N automaticallyupon successfully connecting to the EVSE 120 and establishing acommunication link between the EV 110 and the EVSE 120. Connecting theEV 110 and the EVSE 120 is done differently depending on the type ofcharging. For example, in case of wired charging, the EV operatorconnects the EV 110 and the EVSE 120 through use of a charging cable. Inthe case of inductive charging, typically the EV operator drives theircar in proximity with a charging pad, which may automatically trigger awireless communications session between EV and EVSE; or the EV operatormay be required to press a button to connect the EV with the EVSE 120.

In another embodiment, an EV operator profile for an EV operator is madeavailable to an application on a mobile communication device (e.g., asmartphone, a cell phone, a tablet, etc.) that the EV operator can usewhen requesting charging service. The EV operator profile may be storedlocally on the application and/or on the network server 125 andavailable to the application. As an example, an EV operator may requestcharging service at the EVSE 120 using the application and the EVoperator profile may be then transmitted to the EVSE 120 (e.g., from themobile communication device itself if the data is stored therein or fromthe network server 125).

After the EV 110 is connected with the EVSE 120, EV operator-specificparameters 140 are transmitted to the EVSE 120 over the communicationlink 115. The communication link 115 may be a wired connection and/or awireless connection. For example, in the case of a wired connectionbetween the EV and the EVSE where typically a charging cable connectsthe EV and EVSE, the EV operator-specific parameters may be communicatedto the EVSE across the charging cable. As another example, a wirelessconnection may be established between the EV and the EVSE that can beused to communicate the EV operator-specific parameters (which may berequired in case of inductive charging). The wireless connection may bea personal area network (PAN) connection such as Bluetooth. Thecommunication link 115 may be compliant with such industry standards asISO/IEC 15118, and SAE J2847/J2931. A TCP/IP session may be establishedsuch that the EVSE 120 (or attached device in the network) assigns an IPaddress (through DHCP) to the EV 110 and trustworthiness is determinedbased on certificate chains. As another example, the communication link115 may use a network connection from a mobile device (e.g., a cellphone, smartphone, tablet, etc.) that may transfer the operator-specificparameters to the EVSE 120.

As previously described, the EV operator-specific parameters may affectthe charging services of that EV operator. For example, the EVoperator-specific parameters may include access credentials of that EVoperator that determine whether the EV operator is allowed to use theEVSE 120 at the time of the request. Upon receiving the EVoperator-specific parameters, the EVSE 120 applies or affects thoseoperator-specific parameters accordingly. For example, in the case ofreceiving access credentials, the EVSE 120 may use those accesscredentials to determine whether the EV operator is allowed to use theEVSE 120. As another example, if the EV operator-specific parametersincludes one or more notification message preferences that define one ormore events of interest in which the EV operator wishes to receive anotification message, the EVSE 120 may determine whether, when, and/orwhere to transmit a notification message upon detecting a notificationevent of interest based at least on the notification messagepreferences.

The EVSE 120 may periodically receive other information that may affectthe charging service of the EV 110. For example, the EVSE 120 mayreceive demand response event information (e.g., from a utilitysupplying energy to the EVSE) and determine whether to act according tothe EV operator-specific parameters received from the EV 110. Forexample, the EV operator-specific parameter may indicate that the EVoperator is subject to having their charging service limited and/or shutoff during a demand response event (period of high demand), and the EVSE120 can cause the charging service to act accordingly upon such anevent. As another example, the EVSE 120 may receive pricing changes fromthe network server 125 over the communication link 135.

FIG. 2 is a flow diagram that illustrates exemplary operations accordingto some embodiments of the invention. The operations of FIG. 2 will bedescribed with respect to FIG. 1. The electric vehicle 110 is connectedto the EVSE 120 at operation 210. As described above, the EV 110 can beconnected to the EVSE 120 differently depending on the type of chargingsupported (e.g., wired charging or wireless charging). Next, atoperation 215, the communication link 115 is established between the EV110 and the EVSE 120.

Next, at operation 220, the EVSE 120 receives, from the connected EV 110over the communication link 115, one or more EV operator-specificparameters that are specific to an EV operator. In one embodiment, theEV operator-specific parameter(s) are automatically sent to the EVSE 120(without further EV operator intervention). In another embodiment, theEV operator-specific parameter(s) are sent to the EVSE 120 upon requestof the EVSE 120 or the EV operator. For example, the EV operator may beprompted to select a profile to transmit to the EVSE 120 (e.g., on ascreen of a mobile application) after connecting to the EVSE 120. In oneembodiment, after receiving the EV operator-specific parameters, theEVSE 120 caches the parameters.

In some cases there may be multiple EV operator profiles available onthe EV 110 to communicate with the EVSE 120. In one embodiment, each EVoperator profile is communicated to the EVSE 120 upon connection of theEV 110. In such an embodiment, the appropriate EV operator profile isselected. For example, the EV operator may be prompted via a mobileapplication or a screen on the EVSE to select the appropriate EVoperator profile.

In another embodiment, an EV operator profile is selected and thatselected EV operator is transmitted to the EVSE 120. For example, the EVoperator may be prompted to select a profile to transmit to the EVSE 120(e.g., on a screen of a mobile application) after connecting to the EVSE120. As another example, the EV 110 may be configured to automaticallyselect the appropriate EV operator profile based on current settings onthe EV 110 that are tied to a particular EV operator (e.g., mirrorsettings, seat position, etc.) and/or based on the car key being used,which may be overridden on the dashboard of the EV 110.

Next, at operation 225, the EVSE 120 applies or affects the one or moreEV operator-specific parameters accordingly, as described above. In someembodiments, the EVSE 120 applies the parameters directly. In otherembodiments, the EVSE 120 does not apply the parameters directly, butinstead interacts with the network server 125 to apply the parameters.By way of example, in the case of access credentials being part of theEV operator-specific parameters, in one embodiment the EVSE 120 receivesthe access credentials from the EV 110, transmits the access credentialsto the network server 125 over the communication link 135, the networkserver 125 determines using the access credentials whether to allowcharging service and communicates the result back to the EVSE 120, andthe EVSE 120 allows/denies charging service to the EV 110 accordingly.For instance, the EVSE 120 may include a power control device thatenergizes a charging port in response to receiving a communication fromthe network server 125 to allow charging service. As another example, ifthe EV operator-specific parameters includes one or more notificationmessage preferences that define one or more events of interest in whichthe EV operator wishes to receive a notification message, the EVSE 120transmits the access credentials to the network server 125 over thecommunication link 135 and the network server 125 determines, using thenotification message preference(s) whether, when, and/or where totransmit a notification message upon detecting a notification event ofinterest.

FIG. 3 illustrates an exemplary embodiment of an EVSE 300 according toone embodiment. The EVSE 120 may take the form of the EVSE 300. Itshould be understood that FIG. 3 illustrates an exemplary architectureof an EVSE, and other, different architectures may be used inembodiments described herein. Although several components areillustrated as being included in the EVSE 300, in some embodimentsadditional, different, or less components may be used in the EVSE 300.For example, some EVSEs may not include a display, a user interface, anRFID reader, and/or a VIN reader.

As illustrated in FIG. 3, the EVSE 300 includes the energy meter 310,the power control device 315, the charging port 320, the volatile memory325, the non-volatile memory 330 (e.g., hard drive, flash, PCM, etc.),one or more transceiver(s) 335 (e.g., wired transceiver(s) (e.g.,Ethernet, power line communication (PLC), etc.) and/or wirelesstransceiver(s) (e.g., 802.15.4 (e.g., ZigBee, etc.), Bluetooth, WiFi,Infrared, GPRS/GSM, CDMA, etc.)), the RFID reader 340, the display unit345, the user interface 350, the processing system 355 (e.g., one ormore microprocessors and/or a system on an integrated circuit), and theVIN reader 360, which are coupled with one or more buses 365.

The energy meter 310 measures the amount of electricity that is flowingon the power line 305 through the charging port 320. While in oneembodiment the energy meter 310 measures current flow, in an alternativeembodiment the energy meter 310 measures power draw. The energy meter310 may be an induction coil or other devices suitable for measuringelectricity. In some embodiments, the energy meter 310 is a programmabletime of use energy meter (e.g., programmed according to the prices andtime periods defined by its host). While the energy meter 310 isillustrated as being included within the EVSE 300, in other embodimentsthe energy meter 310 is exterior to the EVSE 300 but capable ofmeasuring the amount of electricity flowing on the power line 305through the charging port 320.

The charging port 320 is a power receptacle, circuitry for an attachedcharging cord (e.g., with a SAE J1772 connector), or circuitry forinductive charging. While FIG. 3 illustrates a single charging port 320,the EVSE 300 may include multiple charging ports that may be ofdifferent types.

The power control device 315 is a solid-state device that is used tocontrol the current flowing on the power line 305 or any other devicesuitable for controlling the current flowing on the power line 305. Thepower control device 315 may be a set of contactors or relays. In someembodiments the power control device 315 energizes the charging port 320(e.g., by completing the circuit to the power line 305) or de-energizesthe charging port 320 (e.g., by breaking the circuit to the power line305). In some embodiments the power control device 315 energizes thecharging port 320 responsive to a determination that charging service isauthorized for the charging port 320 (e.g., in response to receiving acommunication from the network server 125 to allow charging service).

The RFID reader 340 reads RFID tags from RFID enabled devices (e.g.,smartcards, key fobs, contactless credit cards, etc.), embedded withRFID tag(s) of operators that want to use the charging port 320 of theEVSE 300. For example, in some embodiments a vehicle operator canwave/swipe an RFID enabled device near the RFID reader 340 to provide anidentifier or access credentials for use of the charging port 320. TheRFID identifier may be associated with an electric vehicle. For example,each electric vehicle of a fleet may have an associated RFID enableddevice (e.g., smartcard, key fobs, etc.) configured with the uniqueidentifier of the electric vehicle that an operator can wave/swipe nearthe RFID reader to provide the identifier of the electric vehicle to theEVSE. The vehicle identifier may be transmitted to a server network foridentification of the operator who swiped the RFID enabled device.Electric vehicle operators may use the RFID reader 340 for payment. Inaddition to an RFID reader, the EVSE 300 may also include a credit cardreader.

The transceiver(s) 335 transmit and receive messages. For example, thetransceiver(s) 335 may transmit the set of EV operator-specificparameters to the network server 125. The transceiver(s) 335 may receivea message from the network server 125 to allow charging service or denycharging service.

The display unit 345 is used to display messages to vehicle operatorsincluding charging status, confirmation messages, error messages,notification messages, etc. The display unit 345 may also displayparking information if the EVSE 300 is also acting as a parking meter(e.g., amount of time remaining in minutes, parking violation, etc.).

The user interface 350 allows users to interact with the EVSE 300. Byway of example, the user interface 350 allows electric vehicle operatorsto present user identifiers, be placed in a queue for the charging port320, enter in account and/or payment information, etc.

The processing system 355 may retrieve instruction(s) from the volatilememory 325 and/or the non-volatile memory 330, and execute theinstructions to perform operations as previously described herein. TheVIN reader 360 reads an identifier of an electric vehicle such as theVIN of the electric vehicle.

FIG. 4 is a block diagram illustrating an exemplary architecture of adata processing system that may be used in some embodiments. It shouldbe understood that while FIG. 4 illustrates various components of a dataprocessing system, it is not intended to represent any particulararchitecture or manner of interconnecting the components as such detailsare not germane to the present invention. The network server 125 may usean architecture similar to the architecture of the data processingsystem illustrated in FIG. 4. However, it should be appreciated that thenetwork server 125 may use a different data processing system than thedata processing system 400 or may have fewer, less, more, or differentcomponents than the data processing system 400.

As illustrated in FIG. 4, the data processing system 400, which is aform of a computing device, includes the bus(es) 450 which is coupledwith the processing system 420, power supply 425, memory 430, and thenonvolatile memory 440 (e.g., a hard drive, flash memory, Phase-ChangeMemory (PCM), etc.). The bus(es) 450 may be connected to each otherthrough various bridges, controllers, and/or adapters as is well knownin the art. The processing system 420 may retrieve instruction(s) fromthe memory 430 and/or the nonvolatile memory 440, and execute theinstructions to perform operations as described above. The bus 450interconnects the above components together and also interconnects thosecomponents to the display controller & display device 470, Input/Outputdevice(s) 480 (e.g., NIC (Network Interface Card), a cursor control(e.g., mouse, touchscreen, touchpad, etc.), a keyboard, etc.), and thetransceiver(s) 490 (wired transceiver(s) (e.g., Ethernet, power linecommunication (PLC), etc.) and/or wireless transceiver(s) (e.g.,802.15.4 (e.g., ZigBee, etc.), Bluetooth, WiFi, Infrared, GPRS/GSM,CDMA, RFID, etc.)).

As described herein, instructions may refer to specific configurationsof hardware such as application specific integrated circuits (ASICs)configured to perform certain operations or having a predeterminedfunctionality or software instructions stored in memory embodied in anon-transitory computer readable medium. Thus, the techniques shown inthe figures can be implemented using code and data stored and executedon one or more electronic devices (e.g., a network server, an EVSE).Such electronic devices store and communicate (internally and/or withother electronic devices over a network) code and data usingcomputer-readable media, such as non-transitory computer-readablestorage media (e.g., magnetic disks; optical disks; random accessmemory; read only memory; flash memory devices; phase-change memory) andtransitory computer-readable communication media (e.g., electrical,optical, acoustical or other form of propagated signals—such as carrierwaves, infrared signals, digital signals). In addition, such electronicdevices typically include a set of one or more processors coupled to oneor more other components, such as one or more storage devices(non-transitory computer-readable storage media), user input/outputdevices (e.g., a keyboard, a touchscreen, and/or a display), and networkconnections. The coupling of the set of processors and other componentsis typically through one or more busses and bridges (also termed as buscontrollers). Thus, the storage device of a given electronic devicetypically stores code and/or data for execution on the set of one ormore processors of that electronic device. Of course, one or more partsof an embodiment of the invention may be implemented using differentcombinations of software, firmware, and/or hardware.

While the flow diagrams in the figures show a particular order ofoperations performed by certain embodiments of the invention, it shouldbe understood that such order is exemplary (e.g., alternativeembodiments may perform the operations in a different order, combinecertain operations, overlap certain operations, etc.).

While the invention has been described in terms of several embodiments,those skilled in the art will recognize that the invention is notlimited to the embodiments described, can be practiced with modificationand alteration within the spirit and scope of the appended claims. Thedescription is thus to be regarded as illustrative instead of limiting.

What is claimed is:
 1. A method in an electric vehicle supply equipment(EVSE), comprising: receiving, at the EVSE from an electric vehicle (EV)connected to the EVSE, one or more electric vehicle (EV)operator-specific parameters that are specific to an EV operator,wherein the one or more EV operator-specific parameters affect chargingservice for the EV at the EVSE, wherein the one or more EVoperator-specific parameters are received automatically as a result ofthe EV being connected to the EVSE; and applying the one or more EVoperator-specific parameters to affect charging service for the EV atthe EVSE.
 2. The method of claim 1, wherein the one or more EVoperator-specific parameters includes an access credential, and whereinapplying the one or more EV operator-specific parameters includesdetermining, based at least on the received access credential, whetherto allow use of the EVSE.
 3. The method of claim 1, wherein the one ormore EV operator-specific parameters includes one or more notificationmessage preferences that define one or more events of interest in whichthe EV operator wishes to receive a notification message; and whereinapplying the one or more EV operator-specific parameters includesdetermining, based at least on the received one or more notificationmessage preferences, whether to send the notification message to the EVoperator upon detecting an event of interest.
 4. The method of claim 1,further comprising: wherein the one or more EV operator-specificparameters includes an access credential; and wherein applying oraffecting the one or more EV operator-specific parameters includes:transmitting at least the access credential to a network server that iscommunicatively coupled with the EVSE, responsive to transmitting atleast the access credential to the network sever, receiving from thenetwork server an indication of whether to allow use of the EVSE, andresponsive to receiving an indication from the network server to allowuse, allowing use of the EVSE.
 5. The method of claim 1, wherein the oneor more EV operator-specific parameters are received from the EV over acommunication link that is wired.
 6. The method of claim 5, wherein thecommunication link is across a charging cable that couples the EV andthe EVSE.
 7. The method of claim 1, wherein the one or more EVoperator-specific parameters are received from the EV over acommunication link that is wireless.
 8. An electric vehicle supplyequipment (EVSE), comprising: a processor; and a non-transitorycomputer-readable storage medium that provides instructions that, whenexecuted by the processor, causes said processor to perform thefollowing operations: receive, at the EVSE from an electric vehicle (EV)connected to the EVSE, one or more EV operator-specific parameters thatare specific to an EV operator, wherein the one or more EVoperator-specific parameters affect charging service for the EV at theEVSE, wherein the one or more EV operator-specific parameters arereceived automatically as a result of the EV being connected to theEVSE, and apply the one or more EV operator-specific parameters toaffect charging service for the EV at the EVSE.
 9. The apparatus ofclaim 8, wherein the one or more EV operator-specific parametersincludes an access credential, and wherein application of the one ormore EV operator-specific parameters includes determining, based atleast on the received access credential, whether to allow use of theEVSE.
 10. The apparatus of claim 8, wherein the one or more EVoperator-specific parameters includes one or more notification messagepreferences that define one or more events of interest in which the EVoperator wishes to receive a notification message; and whereinapplication of the one or more EV operator-specific parameters includesdetermining, based at least on the received one or more notificationmessage preferences, whether to send the notification message to the EVoperator upon detecting an event of interest.
 11. The apparatus of claim8, wherein the non-transitory computer-readable storage medium furtherprovides instructions that, when executed by the processor, causes saidprocessor to further perform the following operations: wherein the oneor more EV operator-specific parameters includes an access credential;and wherein application of the one or more EV operator-specificparameters includes: transmitting at least the access credential to anetwork server that is communicatively coupled with the EVSE, responsiveto transmitting at least the access credential to the network sever,receiving from the network server an indication of whether to allow useof the EVSE, and responsive to receiving an indication from the networkserver to allow use, allowing use of the EVSE.
 12. The apparatus ofclaim 8, wherein the one or more EV operator-specific parameters arereceived from the EV over a communication link that is wired.
 13. Theapparatus of claim 12, wherein the communication link is across acharging cable that couples the EV and the EVSE.
 14. The apparatus ofclaim 8, wherein the one or more EV operator-specific parameters arereceived from the EV over a communication link that is wireless.
 15. Anon-transitory computer-readable storage medium of an electric vehiclesupply equipment (EVSE) that provides instructions that, when executedby a processor of the EVSE, will cause the EVSE to perform operationscomprising: receiving, at the EVSE from an electric vehicle (EV)connected to the EVSE, one or more EV operator-specific parameters thatare specific to an EV operator, wherein the one or more EVoperator-specific parameters affect charging service for the EV at theEVSE, wherein the one or more EV operator-specific parameters arereceived automatically as a result of the EV being connected to theEVSE; and applying the one or more EV operator-specific parameters toaffect charging service for the EV at the EVSE.
 16. The non-transitorycomputer-readable storage medium of claim 15, wherein the one or more EVoperator-specific parameters includes an access credential, and whereinapplying the one or more EV operator-specific parameters includesdetermining, based at least on the received access credential, whetherto allow use of the EVSE.
 17. The non-transitory computer-readablestorage medium of claim 15, wherein the one or more EV operator-specificparameters includes one or more notification message preferences thatdefine one or more events of interest in which the EV operator wishes toreceive a notification message; and wherein applying the one or more EVoperator-specific parameters includes determining, based at least on thereceived one or more notification message preferences, whether to sendthe notification message to the EV operator upon detecting an event ofinterest.
 18. The non-transitory computer-readable storage medium ofclaim 15, further comprising: wherein the one or more EVoperator-specific parameters includes an access credential; and whereinapplying or affecting the one or more EV operator-specific parametersincludes: transmitting at least the access credential to a networkserver that is communicatively coupled with the EVSE, responsive totransmitting at least the access credential to the network sever,receiving from the network server an indication of whether to allow useof the EVSE, and responsive to receiving an indication from the networkserver to allow use, allowing use of the EVSE.
 19. The non-transitorycomputer-readable storage medium of claim 15, wherein the one or more EVoperator-specific parameters are received from the EV over acommunication link that is wired.
 20. The non-transitorycomputer-readable storage medium of claim 19, wherein the communicationlink is across a charging cable that couples the EV and the EVSE. 21.The non-transitory computer-readable storage medium of claim 15, whereinthe one or more EV operator-specific parameters are received from the EVover a communication link that is wireless.